Skip to content

Update dependency bref/symfony-bridge to v3 - #2662

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/services/bref-symfony-bridge-3.x
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/services/bref-symfony-bridge-3.x

Conversation

@renovate

@renovate renovate Bot commented Oct 21, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
bref/symfony-bridge ^2 → ^3 age confidence

Release Notes

brefphp/symfony-bridge (bref/symfony-bridge)

v3.0.3

Compare Source

Uploaded files are deleted

When a Symfony application runs with the Bref runtime (not PHP-FPM), the files uploaded with a request were never deleted: they stayed in the Lambda instance's /tmp until it was full, and then everything that writes to /tmp failed. They are now deleted when the next request starts.

On Bref 3, Bref 3.0.13 is now required: before it, Bref's cleanup missed every upload on PHP 8.4 and up.

What's Changed

Full Changelog: brefphp/symfony-bridge@3.0.2...3.0.3

v3.0.2

Compare Source

Bref's log formatter is now enabled on new applications

The bundle that enables Bref's CloudWatch log formatter was never registered by Symfony Flex, so Symfony applications logged Monolog's default JSON instead. The bundle is now named BrefSymfonyBridgeBundle, which Flex adds to config/bundles.php when installing bref/symfony-bridge.

Existing applications: nothing changes and nothing breaks. Flex doesn't register bundles when a package is updated, so your logs keep their current format. To switch to Bref's log format, add this line to config/bundles.php:

Bref\SymfonyBridge\BrefSymfonyBridgeBundle::class => ['all' => true],

If you had registered Bref\SymfonyBridge\BrefBundle yourself, it keeps working. It is deprecated in favor of BrefSymfonyBridgeBundle.

Request ID in logs

bref/monolog-bridge 2.0 is now supported: with Bref's log formatter, each log line starts with the ID of the Lambda invocation that wrote it, so that all the logs of a request can be found in Bref Cloud or in CloudWatch Logs Insights (documentation). To keep the previous format, require bref/monolog-bridge: ^1.0 in your application.

What's Changed

Full Changelog: brefphp/symfony-bridge@3.0.1...3.0.2

v3.0.1

Compare Source

What's Changed

Full Changelog: brefphp/symfony-bridge@2.0.1...3.0.1

v3.0.0

Compare Source

Bref 3.0 is released 🎉

Read the full blog post here: bref.sh/news/03-bref-3.0

The full upgrade guide is here: https://bref.sh/docs/upgrading/v3

Bref v3

What's Changed

Full Changelog: brefphp/symfony-bridge@1.2.0...3.0.0


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
renovate Bot requested a review from ryanmab as a code owner October 21, 2026 19:27
@renovate renovate Bot added bump-patch Pull request which needs to bump a patch version in this repository. chore Pull requests that resolve chores (for releases) dependencies Pull requests that update a dependency file php Pull requests that update Php code labels Oct 21, 2026
@github-actions

github-actions Bot commented Oct 21, 2026 •

Copy link
Copy Markdown

Terraform plan in ./services/orchestrator/infrastructure in the prod workspace
With var files: ./services/orchestrator/infrastructure/prod.tfvars

Plan: 0 to add, 1 to change, 0 to destroy.
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
!~  update in-place

Terraform will perform the following actions:

  # module.orchestrator.aws_lambda_function.service will be updated in-place
!~  resource "aws_lambda_function" "service" {
        id                             = "coverage-orchestrator-prod"
!~      last_modified                  = "2026-10-21T19:18:41.000+0000" -> (known after apply)
!~      source_code_hash               = "ZooNMsQekn7Hgv1eZZWAAuzc19xDsgpypilSaj8brnc=" -> "WlDnf660aybSdSfSIA5QOHQ8Z1Ff6jiZtuua8gjFmz8="
        tags                           = {}
#        (30 unchanged attributes hidden)

#        (4 unchanged blocks hidden)
    }

Plan: 0 to add, 1 to change, 0 to destroy.

Warning: Argument is deprecated

  with module.event_store.aws_dynamodb_table.event_table,
  on event_store/main.tf line 1, in resource "aws_dynamodb_table" "event_table":
   1: resource "aws_dynamodb_table" "event_table" {

hash_key is deprecated. Use key_schema instead.

(and one more similar warning elsewhere)

📝 Plan generated in Orchestrator #2665

@github-actions

github-actions Bot commented Oct 21, 2026 •

Copy link
Copy Markdown

Terraform plan in ./services/publish/infrastructure in the prod workspace
With var files: ./services/publish/infrastructure/prod.tfvars

Plan: 0 to add, 1 to change, 0 to destroy.
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
!~  update in-place

Terraform will perform the following actions:

  # module.publish.aws_lambda_function.service will be updated in-place
!~  resource "aws_lambda_function" "service" {
        id                             = "coverage-publish-prod"
!~      last_modified                  = "2026-10-21T19:19:01.000+0000" -> (known after apply)
!~      source_code_hash               = "ixRCUlILQ9xZ/BhGCm+pMoylYcKOpXOzJEWMwThOUq4=" -> "YATbCkt6LtQGX9/EWvCjX64zH2xIXTe5YOizSkqbnnc="
        tags                           = {}
#        (30 unchanged attributes hidden)

#        (4 unchanged blocks hidden)
    }

Plan: 0 to add, 1 to change, 0 to destroy.

📝 Plan generated in Publish #2857

@github-actions

github-actions Bot commented Oct 21, 2026 •

Copy link
Copy Markdown

Terraform plan in ./services/ingest/infrastructure in the prod workspace
With var files: ./services/ingest/infrastructure/prod.tfvars

Plan: 0 to add, 1 to change, 0 to destroy.
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
!~  update in-place

Terraform will perform the following actions:

  # module.ingest.aws_lambda_function.service will be updated in-place
!~  resource "aws_lambda_function" "service" {
        id                             = "coverage-ingest-prod"
!~      last_modified                  = "2026-10-21T19:19:12.000+0000" -> (known after apply)
!~      source_code_hash               = "YB5eU4Sk6TyoBJG3r+aYNaSY4FajZRLe0ybJ+y6Ffws=" -> "BhOn0XMMqoqezs0zBMflra8zmGW1iDF1fCeE4nczWSg="
        tags                           = {}
#        (30 unchanged attributes hidden)

#        (4 unchanged blocks hidden)
    }

Plan: 0 to add, 1 to change, 0 to destroy.

📝 Plan generated in Ingest #3640

@github-actions

github-actions Bot commented Oct 21, 2026 •

Copy link
Copy Markdown

Terraform plan in ./services/api/infrastructure in the prod workspace
With var files: ./services/api/infrastructure/prod.tfvars

Plan: 0 to add, 3 to change, 0 to destroy.
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
!~  update in-place

Terraform will perform the following actions:

  # module.api.aws_lambda_function.api will be updated in-place
!~  resource "aws_lambda_function" "api" {
        id                             = "coverage-api-prod"
!~      last_modified                  = "2026-10-21T19:19:47.000+0000" -> (known after apply)
!~      source_code_hash               = "yV9DzMxqaHvQLJi94N94Ez+q/ZeCHf4GSxSlx3zLU24=" -> "0iBEH/UlvtPLG+lKqYwDRT/L3RZgMuvwa1nXV2SvTfA="
        tags                           = {}
#        (30 unchanged attributes hidden)

#        (4 unchanged blocks hidden)
    }

  # module.event_listener.aws_lambda_function.events will be updated in-place
!~  resource "aws_lambda_function" "events" {
        id                             = "coverage-api-event-listener-prod"
!~      last_modified                  = "2026-10-21T19:19:30.000+0000" -> (known after apply)
!~      source_code_hash               = "yV9DzMxqaHvQLJi94N94Ez+q/ZeCHf4GSxSlx3zLU24=" -> "0iBEH/UlvtPLG+lKqYwDRT/L3RZgMuvwa1nXV2SvTfA="
        tags                           = {}
#        (30 unchanged attributes hidden)

#        (4 unchanged blocks hidden)
    }

  # module.webhook_handler.aws_lambda_function.webhooks will be updated in-place
!~  resource "aws_lambda_function" "webhooks" {
        id                             = "coverage-api-webhook-handler-prod"
!~      last_modified                  = "2026-10-21T19:19:39.000+0000" -> (known after apply)
!~      source_code_hash               = "yV9DzMxqaHvQLJi94N94Ez+q/ZeCHf4GSxSlx3zLU24=" -> "0iBEH/UlvtPLG+lKqYwDRT/L3RZgMuvwa1nXV2SvTfA="
        tags                           = {}
#        (30 unchanged attributes hidden)

#        (4 unchanged blocks hidden)
    }

Plan: 0 to add, 3 to change, 0 to destroy.

📝 Plan generated in API #3664

@github-actions

github-actions Bot commented Oct 21, 2026 •

Copy link
Copy Markdown

Terraform plan in ./services/analyse/infrastructure in the prod workspace
With var files: ./services/analyse/infrastructure/prod.tfvars

Plan: 0 to add, 1 to change, 0 to destroy.
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
!~  update in-place

Terraform will perform the following actions:

  # module.analyse.aws_lambda_function.analyse will be updated in-place
!~  resource "aws_lambda_function" "analyse" {
        id                             = "coverage-analyse-prod"
!~      last_modified                  = "2026-10-21T19:19:06.000+0000" -> (known after apply)
!~      source_code_hash               = "fhjUgdyYs4ibQ72cuaShYuL1BPAbhJ+SggiSBWCcfis=" -> "3M/TqGDTXFIkqsE0vV1W/vOhpBaMPleghJ4vXoCipeU="
        tags                           = {}
#        (30 unchanged attributes hidden)

#        (4 unchanged blocks hidden)
    }

Plan: 0 to add, 1 to change, 0 to destroy.

📝 Plan generated in Analyse #3959

@renovate
renovate Bot force-pushed the renovate/services/bref-symfony-bridge-3.x branch from 4b1a4d4 to 5fa896f Compare October 30, 2026 03:41
@coverage-robot

Copy link
Copy Markdown

Coverage Report

Merging #2662 will not change the total coverage (compared to bc7d564)

Total Coverage Diff Coverage
78.03% ø
Tags
Tag Lines Covered Partial Uncovered Coverage
analyse-service 2430 2124 0 306 87.41%
api-service 1420 1015 0 405 71.48%
clients-package
(Carried forward from dd22fbc)
95 88 0 7 92.63%
configuration-package
(Carried forward from dd22fbc)
665 513 0 152 77.14%
event-package
(Carried forward from dd22fbc)
166 107 0 59 64.46%
ingest-service 1040 852 0 188 81.92%
local-package
(Carried forward from dd22fbc)
250 169 0 81 67.6%
message-package
(Carried forward from dd22fbc)
92 56 0 36 60.87%
orchestrator-service 850 704 0 146 82.82%
publish-service 1113 718 0 395 64.51%
telemetry-package
(Carried forward from dd22fbc)
108 75 0 33 69.44%
Impacted Files

No impacted files in #2662

Last update to 5fa896f at 03:44am UTC

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bump-patch Pull request which needs to bump a patch version in this repository. chore Pull requests that resolve chores (for releases) dependencies Pull requests that update a dependency file php Pull requests that update Php code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants